-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bugs related with SpinRange
and flow
#488
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #488 +/- ##
==========================================
+ Coverage 90.27% 90.70% +0.43%
==========================================
Files 54 54
Lines 3055 3046 -9
==========================================
+ Hits 2758 2763 +5
+ Misses 297 283 -14
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Can you explain why this check function Base.getindex(m::Motion, p)
idx, spin_range = m.spins[p]
return idx !== nothing ? Motion(m.action[idx], m.time, spin_range) : nothing
end |
I need this when, for example I have a julia> obj.motion
MotionList(
Translate(..., SpinRange(501:1000))
) When indexing julia> obj[1:500].motion
NoMotion(...) |
Ok! Feel free to merge. |
I discovered these bugs when testing with the artery.phantom (now deleted because of its size, I should upload it to another repository, Zenodo or as an artifact).